home *** CD-ROM | disk | FTP | other *** search
- Path: access1.digex.net!not-for-mail
- From: ell@access1.digex.net (Ell)
- Newsgroups: comp.object,comp.software-eng,comp.lang.c++
- Subject: Re: Moving from C to C++
- Followup-To: comp.object,comp.software-eng,comp.lang.c++
- Date: 13 Jan 1996 23:08:25 GMT
- Organization: The Universe
- Message-ID: <4d9e19$5l@news4.digex.net>
- References: <4cs44p$3pk@ixnews8.ix.netcom.com> <RMARTIN.96Jan9215355@rcm.oma.com> <4cvv3b$1nb@miranda.gmrc.gecm.com> <30F6C628.4354@platinum.com>
- NNTP-Posting-Host: access1.digex.net
- X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
-
- Rud Merriam (merriam@platinum.com) wrote:
- :...
- :I'd recommend Booch, Meilir Page-Jones' "What Every Programmer Should Know
- :About Object-Oriented Design" and then Martin. I'd even suggest more of a
- :skimming of Booch for general perspective and concepts rather than
- :details.
-
- I think there is a lot to learn about oo architecture and design in
- Booch's Object-Oriented Analysis and Design -- in particular for oo
- projects using C++.
-
- Personally, while RMartin showed some good design structures in his book,
- I found it hard to follow his reasoning and choices. I think he could
- have gotten to effective designs earlier by solving more during analysis,
- and taking a wholistsic rather than piecemeal approach to architecture and
- design. I.e. often he went through requirements one by one and created a
- design for each requirement, and although he often later went back to
- search for commonality and underlying mechanisms, I think if he looked at
- requirements wholistically from the start, and formulated a logical
- solution earlier he would have discovered the proper architecture,
- commonality and mechanisms early on.
-
- Elliott
-